-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UIORGS-391 - Settings for banking information #577
Conversation
Use plugins compatible with the requested version of stripes (v9). Refs UIORGS-404
* UIORGS-383: add donor info for organization summary * tests: fix failing tests * tests: remove failing snapshots * tests: generate snapshot tests * tests: update snapshot tests * improve: bump package.json, fix organizations summary layout, remove checkbox handler
src/Settings/BankingAccountTypeSettings/BankingAccountTypeSettings.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettings.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettings.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettings.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update package.json
with the new okapi interfaces and required permissions for new endpoints.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the comments below, note that there are no changes to the CHANGELOG.md
file.
src/Settings/BankingAccountTypeSettings/BankingAccountTypeSettings.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettings.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettings.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettingsForm.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettingsForm.js
Outdated
Show resolved
Hide resolved
src/Settings/BankingInformationSettings/BankingInformationSettings.test.js
Show resolved
Hide resolved
label={<FormattedMessage id="ui-organizations.settings.bankingInformation" />} | ||
name="value" | ||
type="checkbox" | ||
vertical |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think to be consistent we should keep label and checkbox horizontally:
https://folio-snapshot.dev.folio.org/settings/orders/approvals
https://folio-snapshot.dev.folio.org/settings/orders/open-order
https://folio-snapshot.dev.folio.org/settings/orders/instance-matching
https://folio-snapshot.dev.folio.org/settings/invoice/approvals
...
src/Settings/BankingInformationSettings/BankingInformationSettingsForm.test.js
Show resolved
Hide resolved
src/Settings/constants.js
Outdated
export const SETTINGS_API = 'organizations-storage/settings'; | ||
export const BANKING_ACCOUNT_TYPES_API = 'organizations-storage/banking-account-types'; | ||
|
||
export const BANKING_INFORMATION_ENABLED_QUERY_KEY = 'key=BANKING_INFORMATION_ENABLED'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you keep BANKING_INFORMATION_ENABLED
value as a separate const, please?
const ConnectedComponent = stripes.connect(ControlledVocab); | ||
|
||
const columnMapping = { | ||
value: <FormattedMessage id="ui-organizations.settings.name" />, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
value
or name
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
} catch (error) { | ||
sendCallout({ | ||
type: 'error', | ||
message: <FormattedMessage id="settings.accountTypes.save.error.generic.message" />, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
app prefix in the label ID
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and please test if it works correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
src/Settings/constants.js
Outdated
export const BANKING_ACCOUNT_TYPES_API = 'organizations-storage/banking-account-types'; | ||
|
||
export const BANKING_INFORMATION_ENABLED_QUERY_KEY = 'BANKING_INFORMATION_ENABLED'; | ||
export const BANKING_INFORMATION_SEARCH_QUERY = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like search "params" is more appropriate for the const than "query"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
Kudos, SonarCloud Quality Gate passed! |
Purpose
UIORGS-391 - Settings for banking information
Approach
Screen.Recording.2023-11-01.at.5.06.05.PM.mov
TODOS and Open Questions
Learning
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.